What Does This Do

Fixes ./gradlew <task> -PddGradleDebug failing with:

Could not create task ':...:mule-4.5:extractMuleServices'.
> Resolution of the configuration ':...:mule-4.5:muleServices' was attempted without an exclusive lock. This is unsafe and not allowed.

The gradle-debug plugin now inspects tasks from gradle.taskGraph.whenReady (after the execution graph is built and scheduled tasks are fully configured) instead of force-realizing every task in every project from projectsEvaluated.

Motivation

The old code iterated project.tasks inside a projectsEvaluated BuildListener. Iterating the task container realizes every lazily-registered task, running its configuration action. Some tasks (e.g. mule's extractMuleServices, a Sync task) resolve a configuration in that action via resolvedConfiguration.resolvedArtifacts. projectsEvaluated runs without the project's exclusive lock, and current Gradle forbids resolving a configuration there — so the whole build aborted, even for unrelated commands like help.

Moving to taskGraph.whenReady fixes the root cause: at that point the scheduled tasks are already configured under the proper lock, so reading them is safe. It also avoids needlessly realizing every task in the ~200-module tree.

Additional Notes

• Behavioral change: the log now covers tasks in the execution graph of the requested command rather than literally every task. Run it against a real task (build, :module:test); help reports almost nothing.
• Added short usage docs to the plugin header (how to run, where the log lands, meaning of "jdk":"unknown").

🤖 Generated with Claude Code